Recipient

Restrictions on recipients

   Recipients

Disallowed Recipients

This is the list of recipient email addresses that cannot be sent to through your SMTP server. You can use wildcards (e.g. *@*.tw, customerdirect@*.*) or leave blank for no restrictions

Example interface:

Example:jondoe@example.com, exemployee@example.com

Importing data

Press the import button, also shown as >> when the interface is small, to import data into the list.The following file types are supported:

        CSV (Comma delimited) (*.csv)
        Text (Tab delimited) (*.txt)
        All Files (*.*)
        
The data should be separated by commas, tab characters or newlines.
Each data entry must match the validation wildcard '*@*.*'. Entries that do not match will be discarded.
Duplicate entries are not imported more than once.

Only allow email to valid user, group, route or responder addresses

You can ensure that only valid, listed internal recipients may receive email. This includes all email addresses configured for users, their alias, groups, routes and responders.

Example interface:

Options:On/Off

Default:off

   Mass Mailing Prevention

Maximum Recipients Action

this sets what happens to email that exceed the number of recipients specified in MaxRecipients. "Reject" makes the SMTP server reject the email completely. "Limit Recipients" limits the number of recipients of the email. "Close Connection" closes the email client's connection to the email server

Example interface:

Options:Off, Limit Recipients, Reject Mail, Close Connection

Default:Off

Maximum Recipients

This is the maximum number of recipients allowed per incoming email. Email exceeding this number of recipients are processed according to the MaxRecipientsAction setting

Example interface:

Range5 - 2000

Default:32

Example:32

Address Probing Action

A delay can be enforced after every client enquiry into valid email addresses (SMTP VRFY and RCPT TO). This prevents mass probing for valid email addresses. The delay is only inserted after usual numbers of RCPT TO or VRFY commands have been processed: so it wont slow down your ability to receive legitimate email

Example interface:

Default:Off

After

A delay can be enforced after every client enquiry into valid email addresses (SMTP VRFY and RCPT TO). This prevents mass probing for valid email addresses. The delay is only inserted after usual numbers of RCPT TO or VRFY commands have been processed: so it wont slow down your ability to receive legitimate email

Example interface:

Range2 - 2000

Default:32

Example:24

Delay

A delay can be enforced after every client enquiry into valid email addresses (SMTP VRFY and RCPT TO). This prevents mass probing for valid email addresses. The delay is only inserted after usual numbers of RCPT TO or VRFY commands have been processed: so it wont slow down your ability to receive legitimate email

Example interface:

Range1 - 60 seconds

Default:5 seconds

Example:15 seconds

   Botnet Prevention

Botnet...

Botnet prevention settings

Botnets - Botnet Prevention